Skip to content

docs: remove stale scratch artifact files from repo root - #1162

Merged
ogazboiz merged 3 commits into
LabsCrypt:mainfrom
OTimileyin:docs/remove-stale-artifact-files
Aug 3, 2026
Merged

docs: remove stale scratch artifact files from repo root#1162
ogazboiz merged 3 commits into
LabsCrypt:mainfrom
OTimileyin:docs/remove-stale-artifact-files

Conversation

@OTimileyin

@OTimileyin OTimileyin commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Closes #1093

Description

Remove four stale scratch/artifact files (ISSUE_134_SUMMARY.md, PR_DESCRIPTION.md, issue.md, pr.md) that were remnants of a past PR and not referenced by CI, scripts, or documentation anywhere in the codebase. Add .gitignore patterns to prevent similar scratch markdown files from being committed in the future.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔧 Refactoring (no functional changes)
  • ⚡ Performance improvement
  • 🧪 Test addition or update

Related Issues

Closes #1093

Changes Made

  • Removed ISSUE_134_SUMMARY.md (209 lines)
  • Removed PR_DESCRIPTION.md (85 lines)
  • Removed issue.md (73 lines)
  • Removed pr.md (34 lines)
  • Updated .gitignore with scratch file patterns

Testing

Test Coverage

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing performed

Test Steps

  1. Confirmed zero references to the four files across the entire repo (CI, scripts, docs, source)
  2. Verified git status shows only the 5 allowed files were touched
  3. Ran git diff main --stat to confirm changes are scoped correctly

Breaking Changes

None.

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published
  • I have checked for breaking changes and documented them if applicable

Additional Notes

  • pr_102_diff.txt is out of scope per the issue (tracked separately)

OTimileyin and others added 3 commits July 30, 2026 09:02
Closes LabsCrypt#1093

Remove four stale scratch/artifact files (ISSUE_134_SUMMARY.md,
PR_DESCRIPTION.md, issue.md, pr.md) that were remnants of a past PR
and not referenced by CI, scripts, or documentation. Add .gitignore
patterns to prevent similar scratch markdown files from being
committed in the future.

@ogazboiz ogazboiz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

verified the four scratch files are exactly the ones at main's root and pr_102_diff.txt is correctly left per #1093, and the new gitignore patterns do not collide with the issue templates. merging. non-blocking thought for later: anchoring the patterns with a leading slash would avoid ignoring future legit nested files. if you want to keep contributing, join us on Telegram: https://t.me/+DOylgFv1jyJlNzM0

@ogazboiz
ogazboiz merged commit 51c3654 into LabsCrypt:main Aug 3, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] ISSUE_134_SUMMARY.md and PR_DESCRIPTION.md at repo root are stale artifacts from a past PR, not general documentation

2 participants